home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-05
/
3mhs099.zip
/
3MHS.DOC
< prev
next >
Wrap
Text File
|
1992-03-18
|
39KB
|
1,352 lines
3+MHS Gateway
The 3+MAIL/MHS
Connectivity Solution
Version 0.99
March 18, 1992
Copyright (c) 1992 by Brian Dluhy, Howard Kapustein
All Rights Reserved
3+MHS Gateway -2- Version 0.99
1. 3+MHS Shareware Software License
This version of 3+MHS Gateway is NOT public domain or free software, but
is being distributed as "shareware" for EVALUATION PURPOSES ONLY.
1.1. Usage Restrictions
The author(s) grants a limited license to individuals to use this
shareware software for a 30-day evaluation period on a private, non-
commercial basis, for the express purpose of determining whether 3+MHS
Gateway is suitable for their needs. At the end of this 30-day
evaluation period, the individual must either purchase a license from
the author(s) for continued use of the program, or discontinue using
3+MHS Gateway.
What does this mean? If you use this program on a continued basis, you
must purchase a license for its use. 3+MHS Gateway is NOT free, and we
are not giving away free copies. We are giving you the opportunity to
try it before paying for a license for continued use. It is that simple.
Try it. Then either pay for it, or quit using it.
Paying for a license to continue using the software product is not only
required, but also allows the author(s) to provide support and updates,
and continue to provide professional-quality software at reasonable
prices. Licensed users receive printed documentation and a version of
the program that does NOT prefix messages transferred with shareware
reminder text. Registration of the licensed copy allows the registered
user to receive technical support (by phone, BBS, mail, or various
electronic services such as CompuServe), and makes them eligible for
discounts on future versions.
Purchasing a license for 3+MHS Gateway entitles you to use the program
in conjunction with a single MHS and/or 3+MAIL server. If you would like
a multiple-use (site) license, please contact the author(s) for details.
1.2. Distribution, Copying Restrictions
Individuals are granted a limited license to copy the SHAREWARE version
of 3+MHS Gateway only for the trial use of other individuals and subject
to the above limitations. This license DOES NOT include distribution or
copying of this software package:
1. In connection with any other product or service;
2. For general use within a company, institution, or agency;
3. For any consideration or 'disk fee'; or
4. In modified form (i.e., any distribution that does not include ALL
FILES supplied by the author(s) with the shareware version of 3+MHS
Gateway, WITHOUT ALTERATION. This also prohibits distribution of all
or portions of the documentation in printed form.)
3+MHS Gateway -3- Version 0.99
Operators of electronic bulletin board systems (Sysops) are permitted
and encouraged to post the shareware version of 3+MHS Gateway for
downloading by their users, as long as the above conditions are met.
Though a fee may be charged for BBS access, NO FEE may be charged to
specifically access or download the 3+MHS Gateway shareware files.
Non-profit computer-related User Groups may distribute the shareware
version of 3+MHS Gateway provided the above conditions are met. However,
such User Groups MAY charge a NOMINAL fee to cover the cost of the disk
and copying of the software.
Disk vendors MUST obtain written permission from the author(s) before
distributing the shareware version of 3+MHS Gateway. Certain
restrictions apply. Generally, permission is granted. Call or write for
further details.
2. Warranty Disclaimer
THE SHAREWARE VERSION OF 3+MHS GATEWAY IS SUPPLIED "AS IS" AND WITHOUT
ANY WARRANTY. TO THE EXTENT PERMITTED UNDER APPLICABLE LAW, THE
AUTHOR(S) DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO, ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. SPECIFICALLY, THE AUTHOR(S) MAKES NO REPRESENTATION
OR WARRANTY THAT THE SOFTWARE IS FIT FOR ANY PARTICULAR PURPOSE.
THE AUTHOR(S) SHALL NOT BE LIABLE FOR ANY DAMAGES RESULTING FROM THE USE
OF THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO, LOSS OF PROFIT, DATA OR
USE OF THE SOFTWARE, OR SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR
OTHER SIMILAR CLAIMS, EVEN IF THE AUTHOR(S) HAS BEEN SPECIFICALLY
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE
EXCLUSION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE FOREGOING
LIMITATION MAY NOT APPLY TO YOU.
3. Ordering Information
3.1. Licensing
Purchasing a license for 3+MHS Gateway allows you to use the product on
a regular and/or continuing basis. Registration of your licensed copy of
3+MHS Gateway entitles you to technical support from the author(s) and
discounts on updates.
With your purchase, you will receive: a licensed copy of 3+MHS Gateway
V0.99 with a 90-day limited warranty and printed, bound documentation.
In addition, your registration entitles you to a free upgrade to Version
1.00 when available.
ALL PRICES AND DISCOUNTS ARE SUBJECT TO CHANGE WITHOUT NOTICE.
3.2. Site Licenses and Quantity Purchases
3+MHS Gateway -4- Version 0.99
All corporate, business, government or other commercial, public or
private users of 3+MHS Gateway must be licensed. Quantity discounts as
well as site (multi-user) licensing is available. Please call or write
for more information.
If you have special requirements, or need customization, please feel
free to submit them in writing. You may request a license for:
Fixed number of copies. See the discount schedule;
Unlimited number of copies. The fee is $2,500;
Customization of messages and documentation. An additional fee may be
required depending on the extent of changes;
Permission to distribute within your organization;
The fee for a license depends on the estimated number of servers that
will use 3+MHS Gateway. To use the discount schedule below, estimate the
total number of MHS servers you plan to use 3+MHS Gateway in conjunction
with:
Number of MHS servers Price per
(copies) copy
1 $295.00
2-3 $275.00
4-6 $250.00
7-9 $225.00
10 and up $200.00
Please contact the author(s) for site license prices.
Regardless of quantity, only one set of materials will be sent to you.
You may then make as many copies as your are licensed. Upgrades will be
made available upon request.
Reseller inquiries are welcome.
3.3. Orders Outside the U.S./Canada/Mexico
Please send a check drawn on a US bank payable in US dollars. Please add
$5 for to cover overseas shipping.
3+MHS Gateway -5- Version 0.99
3.4. Single License Order Form
Remit to: Brian Dluhy Order Form #9203-OF01
PO BOX 376
Devault, PA 19432 USA
*** 3+MHS Gateway version 0.99, March 1992 ***
* Single-Server License Order Form *
NOTE: We offer quantity discounts and multiple-user licenses.
Call for details.
------------------------------------------------------------------------
Send me:
____ 3+MHS Gateway with Printed Manual.......... @ $295.00 ea $ ______
Includes single-server licensed copy of software (Version
0.99) on dual (5.25/3.5) media, 90-day limited warranty,
spiral-bound indexed manual, free upgrade to version
1.00, low-cost upgrades.
SHIPPING (each copy)... US/Canada/Mexico: $3; Overseas: $10 $ ______
SUBTOTAL $ ______
Pennsylvania Residents please add Sales Tax ........... @ 6% $ ______
TOTAL (U.S. Funds drawn on U.S. Bank) $ ______
Payment by: ( )CHECK ( )MONEY ORDER
Name: _____________________________________________________________
Company (ONLY if company address):_________________________________
Address: __________________________________________________________
: __________________________________________________________
: __________________________________________________________
Voice Day Phone: ______________________ Evening: __________________
PRICES SUBJECT TO CHANGE WITHOUT NOTICE. Call to confirm current
prices.
3+MHS Gateway -6- Version 0.99
4. Credits
4.1. About the Authors
Brian Dluhy
A long time 3Wizard and recent CNE candidate, I first became involved
with 3Com and networks at SMS (Shared Medical Systems) in 1984. At SMS,
I have been involved with supporting our 3Com clients as well as our
large internal 3Plus network. I was a member of the 3Wizard Council as
well as a director of our local 3Com User Group. Since that fateful day
last January, I have been been working on migration issues for our
clients as well as our internal network.
Howard Kapustein
After graduating Rensselaer Polytechnic Institute in May, 1989 (B.S in
Computer Science , minor in Accounting), I joined the ranks of SMS
(Shared Medical Systems) in Malvern, PA in the PC development
department. Since then I've had the opportunity to delve into Microsoft
Windows, OS/2 (2.0!), C++, object-oriented analysis and design, Novell
NetWare, and communications in general. Replacing my old clunker PC with
a Gateway 2000 386/33 has helped my pursuit of consulting and
programming on the side (hint, hint, especially in C/C++ and DOS).
Author of several shareware packages, I still putter when I get a chance
(and the Mrs. let's me :-)
4.2. Acknowledgements
Infinite thanks to Kim for keeping me sane and happy, and letting me
putter at all hours of the day (and night).
Robert Blacher, Sysop of Computer Connections (202-547-2008), for
running an excellent BBS.
3+MHS Gateway -7- Version 0.99
5. Introduction
The 3+MHS Gateway is designed to provide seamless electronic mail
connectivity between 3Com 3+MAIL and Novell Message Handling Service
(MHS) systems and users. All major functionality of the mail systems is
supported, as well as numerous minor features (where possible).
Why version 0.99?
Although extensive testing of all 3+MHS Gateway functionality has been
performed, a complete and thorough test of all probable configurations
is not possible by the author(s). [Microsoft had 3,000+ beta testers for
DOS 5.0 and still missed a few 'features'.] The author(s) feel the
current version of 3+MHS Gateway is firmer and more reliable than many
commercial packages, but a "post-beta" or "preliminary release" period
is felt to be in the best interest of you, the client.
Feedback is welcome. Suggestions to make 3+MHS Gateway more robust,
functional and/or easy to use can be passed on to the author(s) via
mail, phone and/or electronic services.
6. Features
The 3+MHS Gateway provides complete connectivity for 3Com 3+MAIL and
Novell MHS systems and users. Features include:
Runs as a true MHS gateway *OR* as a standalone process
(Currently the *ONLY* native 3+MAIL/MHS gateway);
Multiple addressing options for flexible routing of messages;
Supports all major 3+MAIL and MHS functionality including carbon
copy, attachments, registered mail, and non-delivery notifications;
Optional Blind Carbon Copy support from MHS to 3+MAIL users;
DOS 5.0 aware! Can use available high memory to ease RAM cram;
Optional usage logging to disk for later review;
Extra DaVinci EMail 1.x compatibility;
3+MHS Gateway incorporates many small touches to enhance your
productivity by performing its job in as seamless a manner as possible.
7. System Requirements
The 3+MHS Gateway has the following requirements:
3+MHS Gateway -8- Version 0.99
DOS 3.1+
256K available memory
3Com 3+MAIL 1.3.1+
Novell MHS 1.5+
Concurrent NetWare MHS directory and 3+MAIL access (see below)
NetWare MHS (Directory) Access:
3+MHS Gateway is written in compliance with Novell's guidelines for
writing MHS gateways. All message transfers through MHS are
accomplished by reading and writing files in specific subdirectories.
Thus, 3+MHS requires access to NetWare file services.
3+MAIL (XNS) Access:
3+MHS Gateway relies on CMAIL.EXE to perform all 3+MAIL transfers. The
CMAIL program requires the XNS protocol to be available. Thus, 3+MHS
Gateway requires the XNS protocol loaded in memory.
Several options are available to provide concurrent access to NetWare
and 3+MAIL resources:
3Com 3+Open/NetWare Coexistence
This product allows 3+Open users to access NetWare resources. To use
this product with 3+MHS Gateway, load the XNS protocol stack and the
NetWare coexistence software.
Microsoft LAN Manager/NetWare Coexistence
This product allows LAN Manager users to access NetWare resources.
Configuration requirements are identical to 3Com's 3+Open/NetWare
Coexistence: XNS protocol and NetWare software. [The XNS protocol can
be found in the Global Upgrade LAN Package (GULP) or the 3+ Upgrade
Pack, available from Microsoft.]
Novell 3+/NetWare Coexistence
This product allows 3+/3+Open users to access NetWare resources. To
use this product with 3+MHS Gateway, load the XNS protocol stack and
the NetWare software. [Availability unknown: Novell is not yet
shipping this product.]
OS/2 2.0 ???
An OS/2 2.0 workstation with NetWare file access (via the NetWare
Requester for OS/2) and XNS access (via 3Com XNS drivers in a Virtual
DOS Machine) should provide the services required by 3+MHS Gateway.
Specific configuration details are as yet unknown. Call for more
information. [Availability imminent: IBM is scheduled to ship OS/2
2.0 by March 31, 1992.]
3+MHS Gateway -9- Version 0.99
NOTE: One of these options is required at the workstation running 3+MHS
Gateway. All other workstations can load their normal software.
8. Installation
Actual installation of 3+MHS Gateway is a relatively simple and painless
operation. The most complicated steps involve configuring 3+MAIL and
MHS, particularly adddressing, to operate compatibly. [An unfortunate
reality in today's marketplace of minimal electronic mail standards for
the PC.]
The specific steps encompass:
1. Add 3+MHS Gateway as a MHS gateway
2. Add 3+MHS Gateway as a 3+MAIL gateway
3. Install the distributed 3+MHS Gateway software
4. Configure MHS addresses to be compatible with 3+MAIL
5. Configure 3+MAIL addresses to be compatible with MHS
Steps 4 and 5 may be optional, depending on the 3+MHS Gateway addressing
schemes you choose and your existing mail addresses.
8.1. Adding 3+MHS Gateway as a MHS Gateway
To define a gateway on an MHS server, the following steps should be
taken:
1. From the Main menu, select Manage Directories:
Manage Directories
Manage Connections
MHS utilities
Set up Transport Server
<Done>
Index: Press <?> Help: Press <F1>
3+MHS Gateway -10- Version 0.99
2. From the DIRECTORY MANAGER menu, select routes to workgroups, hosts
and gateways under the Review, add, modify or delete option section.
D I R E C T O R Y M A N A G E R
Set up:
This host
Review, add, modify, or delete:
names of users at this host
routes to workgroups, hosts and gateways
user routes
names of affiliated workgroups
<Done>
3. From the next menu, select Add entry:
Review another list
View current list
Copy list to file
Add entry
Modify entry
Delete entry
4. From the next menu, select Define a gateway:
Define route to a workgroup or host reached
via:
telephone call TO that remote host
telephone call FROM that remote host
intermediary workgroup, host or gateway
internet path
Define a gateway
Index: Press <?> Help: Press <F1>
5. The following menu prompts for the gateway's definition:
A GATEWAY
Host name:
Description:
Gateway version: 64
Gateway commands:
<Done>
Index: Press <?> Help: Press <F1>
Enter the following information:
3+MHS Gateway -11- Version 0.99
A GATEWAY
Host name: 3MHS
Description: 3+Mail/MHS Gateway
Gateway version: 70
Gateway commands: 3+MHS command line
options
<Done>
Index: Press <?> Help: Press <F1>
The italicized text is optional. You may enter any Description you
like, and the Gateway commands should be selected for your particular
configuration. See Section 10. Command Line Options for the list of
3+MHS optional available.
8.2. Adding 3+MHS as a 3+Mail Gateway
To register a gateway in the Name Service, the following steps should be
taken:
1. Create a domain with a name that suggests the target mail system,
e.g. DISOSS. This domain should be defined to be on the network where
the gateway will reside. If done for 3+MAIL internetwork, the DISOSS
domain must exist on each network where gateway service is to be
available. In other words, a single gateway PC can serve a large
internet. There must be no real 3+Mail users in the gateway domain.
2. Create a user in that domain, with the name _GATEWAY. The gateway
user must be registered for mail service, but need not have Share
service. Do not include the gateway user in any groups. Since logging
as the gateway user gives access to all outbound mail, it is a good
idea to assign a difficult-to-remember password to the gateway user.
For the internet case, it is not necessary to define a gateway user on
each network. 3+Mail will forward the message to the network where the
gateway domain exists, and it will be delivered to the gateway user's
inbox on that network, through the normal store-and-forward process.
3. If any foreign users are defined in the gateway domain, they must not
be registered for 3+Mail service.
4. (This step is optional, and relates to the curly brackets naming
discussed below.) Create a property for users in the name service or,
in the internetted case, in each name service in the network, called
Mail Address. Its property should be 50001. Here are the responses for
each of the prompts from 3N AddProp 50001:
Property Type (S) ? <return>
Property Name? "Mail Address" (name actually doesn't matter)
Property Description? (fill in, or leave empty)
Property Length? 200
3+MHS Gateway -12- Version 0.99
Property Format (String)? <return>
Primary Property to add to? "user"
Primary Property to add to? <return>
8.3. Installing 3+MHS Software
To install the 3+MHS Gateway as a true MHS gateway, the following steps
should be taken:
1. Copy all files from the 3+MHS Gateway distribution disk to the
appropriate gateway subdirectory (MHS\MAIL\GATES\3MHS\PUBLIC).
NOTE: MHS represents the root MHS subdirectory. For example, if the MHS
directory is accessed via F:\MHS, the above path would be
F:\MHS\MAIL\GATES\3MHS\PUBLIC.
2. Create the 3+MAIL work file subdirectory
(MHS\MAIL\GATES\3MHS\3MAIL\IN and MHS\MAIL\GATES\3MHS\3MAIL\OUT).
3. Using any text editor, edit the file 3MHS-IN.BAT and change x: in
line 5 (CMAIL /ra x:\MHS\MAIL\GATES\3MHS\3MAIL\IN) to point to your
MHS drive.
4. Using any text editor, edit the file 3MHS-OUT.BAT and change x: in
line 13 (FOR %%F IN (x:\MHS\MAIL\GATES\3MHS\3MAIL\OUT\*.MSG)...) to
point to your MHS drive.
Make sure CMAIL.EXE is accessible to these batch files. If CMAIL.EXE is
not in your PATH, modify 3MHS-*.BAT and SEND1.BAT to run CMAIL via an
explicit pathname (e.g. D:\3MAIL\CMAIL.EXE...).
The installation batch file (3MHSINST.BAT) will automate steps 1 and 2.
To run 3+MHS Gateway as a standalone process, copy all distribution
files to a subdirectory and invoke the 3MHS-IN.BAT and 3MHS-OUT.BAT
files appropriately.
8.4. Addressing 3+MAIL Users from MHS
Although 3+MAIL supports a standard 3-level addressing scheme
(name:domain:organization), MHS only supports a 2-level addressing
scheme (name@workgroup). How you configure MHS depends on the level of
3+Mail addressing you require.
3+MHS Gateway provides the following address conversions from MHS to
3+MAIL via the -M option:
'1' - Non-SMF address only
'2' - Non-SMF address if available, else SMF address
3+MHS Gateway -13- Version 0.99
'3' - SMF address only
These options are mutually exclusive; only one may be in use at a time.
The following table provides examples of address conversions with the
MHS to 3+MAIL addressing options:
-M1 -M2 -M3
John @ Sales -Error- John:Sales John:Sales
John @ Sales JSmith:Sales JSmith:Sales John:Sales
{JSmith:Sales}
John @ Sales JSmith:Sales: JSmith:Sales: John:Sales
{JSmith:Sales:Corporate} Corporate Corporate
None @ 3MAIL -Error- None:3MAIL None:3MAIL
None @ 3MAIL John:Sales John:Sales None:3MAIL
{John:Sales}
None @ 3MAIL JSmith:Sales JSmith:Sales None:3MAIL
{JSmith:Sales}
None @ 3MAIL JSmith:Sales: JSmith:Sales: None:3MAIL
{JSmith:Sales:Corporate} Corporate Corporate
In the other direction, 3+MHS Gateway provides the following address
conversions from 3+MAIL to MHS via the -3 option:
'N' - Name to Name component
'D' - Domain to Workgroup component
'O' - Organization to Workgroup component
'S' - Name:Domain:Organization to Non-SMF component
The 'D' and 'O' options are mutually exclusive; only one may be in use
at a time. All other options may be combined for different addressing
resolution.
Additionally, the -S option may modify the name and/or workgroup
component of a MHS address. The -SNname option specifies the default
name for MHS addresses if -3N is not in effect. The -SWworkgroup option
specifies the default workgroup for MHS addresses if -3D and -3O is not
in effect.
The following tables provide examples of address conversions with the
3+MAIL to MHS addressing options (assuming -SNnoname and -SWnowork):
3+MHS Gateway -14- Version 0.99
-3N -3ND -3NO
JSmith JSmith @ JSmith @ JSmith @
nowork nowork nowork
JSmith:Sales JSmith @ JSmith @ JSmith @
nowork Sales nowork
JSmith:Sales: JSmith @ JSmith @ JSmith @
Corporate nowork Sales Corporate
-3S -3NS
JSmith noname @ nowork JSmith @ nowork
{JSmith } {JSmith }
JSmith:Sales noname @ nowork JSmith @ nowork
{JSmith:Sales} {JSmith:Sales}
JSmith:Sales: noname @ nowork JSmith @ nowork
Corporate {JSmith:Sales:Corpo {JSmith:Sales:Corpo
rate} rate}
-3DS -3OS
JSmith noname @ nowork noname @ nowork
{JSmith } {JSmith }
JSmith:Sales noname @ Sales noname @ nowork
{JSmith:Sales} {JSmith:Sales}
JSmith:Sales: noname @ Sales noname @ Corporate
Corporate {JSmith:Sales:Corpo {JSmith:Sales:Corpo
rate} rate}
-3NDS -3NOS
JSmith JSmith @ nowork JSmith @ nowork
{JSmith } {JSmith }
JSmith:Sales JSmith @ Sales JSmith @ nowork
{JSmith:Sales} {JSmith:Sales}
JSmith:Sales: JSmith @ Sales JSmith @ Corporate
Corporate {JSmith:Sales:Corpo {JSmith:Sales:Corpo
rate} rate}
You must select a set of name addressing options that best meets your
particluar needs. Smaller mail systems may be well suited to the
simpler, non-SMF addressing schemes (e.g. -M3 -3ND) and larger, more
complex mail configurations may require the advanced conversion options
(e.g. -M1 -3S).
8.5. Addressing MHS Users from 3+Mail
Using the DISOSS example, Joe on the DISOSS system can be addressed as
Joe:DISOSS:3Com. Here is how the message is directed to
_GATEWAY:DISOSS:3Com when it is being sent. The following section on
Envelopes, and the section on name expansion in the Theory of Operations
should be read to completely understand this.
3+MHS Gateway -15- Version 0.99
The Mail system notices that there is no user named Joe:DISOSS:3Com
registered for 3+Mail. It goes through a sequence of checks to find out
if DISOSS:3Com is a gateway domain. It does this by checking for the
existence of a _GATEWAY:DISOSS:3Com user. If there is one, it builds an
envelope for the server where the gateway user has an inbox.
Let's assume that Joe is also the full name of the user on DISOSS. In
this case, the ultimate recipient name in the envelope that is delivered
to the gateway is Joe:DISOSS:3Com. Presumably the gateway code can then
direct the message properly to Joe.
Note that since our format for DISOSS user names is the same as 3+Mail
users, it is possible to actually register those users in the Name
Service, as long as they are not registered for 3+Mail server. In other
words, their Mail Server property must be null. It might be desirable to
do this because any user who is registered in the name service can be
included in groups.
If the target mail system has more complicated names, either longer than
the 62-character limit of 3+Mail names, or contains characters that are
illegal in 3+Mail names, it can be handled in two different ways. Both
use the curly braces form of naming:
1. The user can simply type in the curly braces:
{oliveb!hplabs!ucbvax!fred}:Unix:3Com
This exact string is passed through to the gateway without the part
inside the braces being examined in any way by 3+Mail.
2. Fred can be registered in the Name Service. The full mail address can
be stored as a property for Fred. When Fred:Unix:3Com is addressed,
3+Mail goes to the Name Service, retrieves his real Unix address, and
puts it in the envelope.
Using the second option means that Fred can be included in groups in the
Name Service, as well as having the advantage that the full Unix address
does not have to be typed each time. It does, of course, require setting
up the Mail Address property in the Name Service, and entering the
addresses for each user who is to be addressed this way. This is
probably to be used only for regular correspondents.
There is nothing that requires the contents of the curly braces be only
the address. It can also be used to specify processing options, such as
4-hour delivery for MCI. The curly braces form is a way that any
information not used by 3+Mail can be passed through 3+Mail to the
gateway.
8.6. Quick Start Addressing
3+MHS Gateway -16- Version 0.99
3+MAIL and MHS are not inherently compatible at the addressing level.
3+MAIL treats the address as an actual address in hierarchial format.
For the most part, MHS treats addresses similarly, but the "workgroup"
component should more appropriately be called a "router".
Short of redefining your entire list of user addresses (3+MAIL and MHS),
there are a few addressing schemes you can use with nearly 100%
functionality.
On the MHS side, define a gateway to route traffic between 3+MAIL and
MHS. For every 3+MAIL domain you want accessible to MHS users, define "a
workgroup [or host] via an intermediary".
For example, define a gateway called 3MHS. To easily access the 3+MAIL
Sales and Support domains from MHS, add the workgroups Sales and
Support, "Routed via: 3MHS".
On the 3+MAIL side, define a gateway to route traffic between 3+MAIL and
MHS. For every MHS workgroup you want accessible to 3+MAIL users, add a
domain and define an alias _GATEWAY:workgroup that references the MHS
gateway.
For example, define a gateway called _GATEWAY:MHS. To easily access the
MHS Sales and Support workgroups from 3+MAIL, add the domains Sales and
Support and define the aliases _GATEWAY:Sales and _GATEWAY:Support,
which reference the _GATEWAY:MHS user.
MHS users send mail to 3+MAIL users specifying the workgroup/domain and
non-SMF address. For example, an MHS user would send a message to "Bob @
Sales { Bob Smith:Sales:Corp }".
3+MAIL users send mail to MHS users specifying the workgroup/domain. For
example, a 3+MAIL user would send a message to "Bob:Sales:Corp".
This addressing scheme should enable mail access with minimal effort and
fuss. The flaw with this plan is MHS users sending mail to 3+MAIL
addresses without specifying the domain component of the 3+MAIL address.
For example, an MHS user sending a message to "Bob @ Sales { Bob Smith
}" will cause the message to get kicked around between MHS and 3+MHS
Gateway. This issue is currently not resolved (and may not even be
resolvable). Comments and suggestions are welcome.
3+MHS Gateway -17- Version 0.99
9. Command Line Options
3+MHS accepts the following command line parameters:
3MHS [options] gateway_host MHS_temp_area
where options can be one or more of the following:
-? Help
Displays the help screen.
-?? Display Settings
Displays the current settings.
-3[NDOS] MHS->3+MAIL Addressing
This option specifies the addressing conversion for 3+MAIL
routed to MHS. The switch supports the following options:
'N' Name to Name component
'D' Domain to Workgroup component
'O' Organization to Workgroup component
'S' Name:Domain:Organization to Non-SMF component
The 'D' and 'O' options are mutually exclusive; only one may
be in use at a time. All other options may be combined for
different addressing resolution.
See section 8.4 Addressing 3+MAIL Users from MHS for more
details.
-B Support Blind Carbon Copy
If this option is enabled, 3+MHS will transmit a message for each
BCC recipient on 3+MAIL. If disabled, the sender will receive a
non-delivery notification from the gateway for each BCC recipient
on 3+Mail.
-C Install critical-error handler
If this option is enabled, 3+MHS will install its own critical
error handler.
-D DaVinci EMail 1.x compatibility
DaVinci EMail 1.x does not use MHS header keywords to distinguish
between To, Carbon Copy and Blind Carbon Copy recipients. Due to
this non-standard implementation, 3+MHS Gateway will falsely
recognize Carbon Copy recipients as Blind Carbon Copy recipients.
This switch enables 3+MHS Gateway to correctly identify Carbon Copy
recipients from DaVinci EMail 1.x. However, Blind Carbon Copy
recipients are falsely identified as Carbon Copy recipients when
this switch is enabled. You must decide which is preferable for
your particular environment.
3+MHS Gateway -18- Version 0.99
Unknown if DaVinci EMail 2.x complies with the MHS 1.5
specification (and thus would not need this switch).
-I Process Incoming (3+MAIL->MHS) mail
3+MHS will process 3+MAIL messages destined for MHS.
-L Usage Log
If this option is enabled, 3+MHS records all activity and errors in
a log file. The log file is useful for maintenance and
troubleshooting. The default log file, 3MHS.LOG, can be changed by
the option -Lfilename.
-M[1,2,3] 3+MAIL->MHS Addressing
This option specifies the addressing conversion for MHS routed
to 3+MAIL. The switch supports the following options:
-M1 Non-SMF address only
-M2 Non-SMF address if available, else SMF address
-M3 SMF address only
See section 8.4 Addressing 3+MAIL Users from MHS for more
details.
-O Process Outgoing (MHS->3+MAIL) mail
3+MHS will process MHS messages destined for 3+MAIL.
-P Post-Process Outgoing (MHS->3+Mail) mail
3+MHS will process messages destined for 3+MAIL after CMAIL has
been run.
-Q Quiet mode
If this option is enabled, all video output is suppressed.
-S<N|W>d 3+MAIL->MHS 'dummy' values
This option specifies the default, or dummy, values used to
resolve addressing conversion from 3+MAIL to MHS. The switch
supports the following options:
-SNd Name component default value
-SWd Workgroup component default value
See section 8.4 Addressing 3+MAIL Users from MHS for more
details.
-V[C|M] Save video display
If this option is enabled, the screen display when 3+MHS is
executed will be restored on exit. The option -VM is used for
monochrome (MDA or Hercules) display modes; use -VC for all
other display modes.
3+MHS Gateway -19- Version 0.99
WARNING: This option is not guarranteed to work if display
resolutions other than 25x80 text mode are used (e.g. 43/50-
line text mode or graphic modes).
-Yn Disk buffer size
This option specifies the size of the disk buffer (in KB) used for
reading messages and copying/moving attachments (disk writes of
messages are not affected). Values from 1 thru 32 are valid. Larger
buffer sizes improve performance but require more memory.
Simple (on/off) options are enabled by specifying the switch with an
optional plus (+) suffix; disabled by a minus (-) suffix, and toggled by
an asterisk (*) suffix. For example, -C or -C+ enables 3+MHS' critical
error handler, -C- disables it, and -C* toggles the current setting.
The following parameters are required by 3+MHS:
gateway_host 3+MHS directory (e.g. F:\MHS\MAIL\GATES\3MHS\). This
parameter must end with a backslash (\).
MHS_temp_area Directory for temporary files created to process incoming
mail (e.g. F:\MHS\SW\). This parameter must end with a
backslash (\).
If 3+MHS is launched by the MHS Connection Manager, these parameters are
automatically appended to the command line.
10. Environment Variables
3+MHS recognizes the following environment variables:
3MHS-OPTIONS
This environment variables specifies 3+MHS command line options and
is parsed before the 3+MHS command line. For example, the command
SET 3MHSOPTIONS=-L -Y16 will enable usage logging and specifies a
16K disk buffer, unless modified by the command line.
3MHS-GWDIR
This environment variable is used if the gateway_host command line
parameter is not specified. This variable is useful for standalone
(non-MHS launched) operation of 3+MHS.
3MHS-TEMPDIR
3MHS-TEMPDIR
This environment variable is used if the MHS_temp_area command line
parameter is not specified. This variable is useful for standalone
(non-MHS launched) operation of 3+MHS.
3+MHS Gateway -20- Version 0.99
11. Compatibility Issues
There are no known incompatibilities at this time.
12. Support
12.1. Where to Find the Most Current Version
3+MHS Gateway will always be distributed to:
Ask3Com on Compuserve
Novell NetWire on Compuserve
Compuer Connections BBS (202-547-2008)
The Invention Factory BBS (212-431-1254)
12.2. Support for 3+MHS Gateway
Free support is available to registered users for a period of 90 days
after purchase.
Primary support is available via Compuserve. Please send all queries to
Brian Dluhy at account 70317,2357.
Phone support is also available to registered users.
Alternative support channels are being investigated.
12.3. Questions
This space intentionally left blank.
Appendix A. Error Messages
This space intentionally left blank.
Appendix B. 3+MHS Internals
This space intentionally left blank.
3+MHS Gateway -21- Version 0.99
Appendix C. 3MWait - 3+MHS Wait Utility
This space intentionally left blank.
Index
This space intentionally left blank.
3+MHS Gateway -22- Version 0.99